<?php
/**
 * <https://y.st./>
 * Copyright © 2015-2019 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Yst Domain',
	'<{subtitle}>' => 'Alexand(er|ra) Yst&apos;s home on the Internet',
	'<{copyright year}>' => '2015-2019',
	'<{body}>' => <<<END
<img src="/img/logo.svg" alt="logo" class="centred-image" width="512" height="497"/>
<h2>School</h2>
<p>
	I&apos;ve been counting down the terms until I can leave this school.
	In the mean time, I&apos;ve compiled my proposed course schedule up to the point I get to leave.
	It&apos;s subject to change, but here&apos;s what I think I&apos;ll be taking:
</p>
<ol start="0">
	<li>
		<time>2019-09-05</time> (a term on security and other proper programming practices)
		<ul>
			<li>
				CS 4403: Software Engineering 2
			</li>
			<li>
				CS 4404: Advanced Networking and Data Security
			</li>
		</ul>
	</li>
	<li>
		<time>2019-11-14</time> (a term on mathematics)
		<ul>
			<li>
				MATH 1211: Calculus
			</li>
			<li>
				MATH 1302: Discrete Mathematics
			</li>
		</ul>
	</li>
	<li>
		<time>2020-01-30</time> (running out of required courses)
		<ul>
			<li>
				CS 3304: Analysis of Algorithms
			</li>
			<li>
				CS 3308: Information Retrieval
			</li>
		</ul>
	</li>
	<li>
		<time>2020-04-09</time> (my final required course and first elective)
		<ul>
			<li>
				CS 4408: Artificial Intelligence
			</li>
			<li>
				PSYC 1205: Emotional intelligence (EI)
			</li>
		</ul>
	</li>
	<li>
		<time>2020-06-18</time> (a term on how people think)
		<ul>
			<li>
				PSYC 1504: Introduction to Psychology
			</li>
			<li>
				SOC 1502: Introduction to Sociology
			</li>
		</ul>
	</li>
	<li>
		<time>2020</time> (a term on biology)
		<ul>
			<li>
				BIOL 1121: Biology 1 for Health Studies Majors
			</li>
			<li>
				BIOL 1301: Introduction to Biology
			</li>
		</ul>
	</li>
	<li>
		<time>2020</time> (not sure this term will happen)
		<ul>
			<li>
				ECON 1580: Introduction to Economics
			</li>
			<li>
				MATH 1281: Statistical Inference
			</li>
		</ul>
	</li>
	<li>
		<time>2021</time> (if this term happens, a term of completing the final course available to me)
		<ul>
			<li>
				AHIST 1401: Art History
			</li>
		</ul>
	</li>
</ol>
<h2>$a[TLS] certificate update</h2>
<p>
	I&apos;ve been evicted from Opal&apos;s server.
	For now, this website is now on GitHub&apos;s server.
	That means that I can&apos;t control the $a[TLS] certificate, due to the way GitHub&apos;s hosting operates.
	Furthermore, GitHub&apos;s certificate doesn&apos;t match the host name of this website.
	That means that there is necessarily a certificate mismatch here.
	Even if GitHub allowed the use of custom certificates though ...
</p>
<p>
	StartCom is closing down.
	With no other viable gratis certificate authority as far as I know, I would have to go back to using self-signed certificates soon.
	There does not seem to be a viable way for me to keep the website running on my budget and still avoid $a[TLS] certificate errors.
	A certificate mismatch warning doesn&apos;t look any scarier in a Web browser than a self-signed certificate warning, so there&apos;s really no reason for me to even bother looking for a solution to the GitHub certificate issue for the time being.
</p>
<p>
	I can&apos;t say GitHub is one of my Git hosts of choice or anything, but their website hosting made moving away from Opal&apos;s place quick and easy.
	I&apos;m open to other ideas (no dependencies on individual persons, please), but this seems like the best option until I have time to look into getting a $a[VPS].
	With a $a[VPS] rented, I should be able to host more than just my website; I should have the clearnet entrance to my tiny $a[IRC] network back, as well as (once I have time to set it up) a Minetest server.
	For security reasons, I can&apos;t get the onion address back up on a $a[VPS] (hosting on hardware you don&apos;t control should be considered insecure, so I can&apos;t risk my onion keys being jacked by the hosting provider), but connecting to the network from $a[Tor] exit nodes will be allowed.
	(Even if I had the onion address working, connecting over the clearnet from $a[Tor] exit nodes would be allowed; after all, I&apos;m not a monster.)
</p>
<h2>Redaction</h2>
<p>
	My school has requested that I remove my coursework submissions from this website.
	I have done as requested, and in addition, have removed any unnecessary references to the school itself.
	Vague mentions such as &quot;in class, we studied {X}&quot; references remain intact, but unnecessary specification of which school I even attend have been corrected.
	What school I attend is still no secret though, and can be found on any of the multitude of take-down notice pages that have replaced pages previously containing coursework submissions.
	Hopefully the school will be satisfied by this level of redaction.
	So far, $saved_state[censored_pages] pages of this website have been completely redacted in compliance with the school&apos;s demand.
</p>
<p>
	According to the school&apos;s policy, the coursework archive can go live again two calendar years after my final term here.
	If everything goes according to plan, <del>I&apos;ll graduate mid-2020</del> <ins>my final term will be some time in 2021</ins>, meaning the archive can and will go live again on <del><time>2023-01-01</time></del> <ins><time>2024-01-01</time></ins>.
	<mark>As of last website update, that&apos;ll be in <del>$saved_state[days_until_freedom_as_of_last_canary_chirp]</del> <ins>$saved_state[days_until_freedom_as_of_last_canary_chirp_extended]</ins> days.</mark>
	That&apos;s right: we even have an automated countdown for the event!
	I can&apos;t predict what my normal update schedule will be at that time, but I&apos;ll likely throw in a special update on that day just to reopen the archive and present new things that will have been literally waiting years to be released.
</p>
<p>
	<ins>Plans have changed, and I&apos;m going to try to take some unnecessary courses.
	If I succeed in getting those courses, it&apos;ll add two terms, pushing me into a new calendar year, thus adding another year to the censorship duration.
	The relevant changes are marked above, but being unsure if I&apos;ll be able to take said extra courses, the added censorship time is not set in stone.</ins>
</p>
<h2>Canary update schedule</h2>
<p>
	I used to try to update my <a href="/a/canary.txt">canary</a> daily, but I have too much on my plate to make that feasible.
	During busy periods, I&apos;m now updating once each week on Wednesdays.
	During slower periods, I&apos;m resting a bit and not updating the canary at all.
	Just before my break periods, my canary chirp will be delayed by one day, falling instead on a Thursday.
	Don&apos;t be alarmed if a scheduled update is missed, there are reasons this might happen.
	However, if the canary doesn&apos;t chirp in over a month, something is definitely wrong.
	(Though unlikely, the &quot;something wrong&quot; might be as minor as a technical error.)
	Currently, the predicted canary update schedule is as follows:
</p>
<ul>
{$¢_build_term_update_schedule(2019, 9, 5)}
{$¢_build_term_update_schedule(2019, 11, 14)}
{$¢_build_term_update_schedule(2020, 1, 30)}
{$¢_build_term_update_schedule(2020, 4, 9)}
{$¢_build_term_update_schedule(2020, 6, 18)}
	<li>
		...
	</li>
	<li>
		Sunday, 2024-01-01
	</li>
</ul>
END
);
